Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Expose cdn settings as params #1204

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

bradbeam
Copy link
Contributor

This moves the configuration of much of the cdn (js/css) into the configuration
so they can be more easily maintained.

Signed-off-by: Brad Beam [email protected]

@LisaFC
Copy link
Collaborator

LisaFC commented Sep 5, 2022

Thanks for this! This is a potentially interesting approach (especially as we have some users who don't necessarily want to use our chosen CDNs), but is presumably going to break any site that doesn't update their config.toml/yaml

Thoughts @chalin @geriom @emckean?

@fekete-robert
Copy link
Collaborator

Maybe we could use the default function of hugo, and use the config parameters if set, or use the original cdns if not.

@LisaFC
Copy link
Collaborator

LisaFC commented Sep 13, 2022

I'll have a look at how the scripts partial would look if we used defaults.

@bradbeam
Copy link
Contributor Author

Sorry for the delay, I just pushed up changes to include defaults inside the templates.

This moves the configuration of much of the cdn (js/css) into the configuration
so they can be more easily maintained.

Signed-off-by: Brad Beam <[email protected]>
@deining
Copy link
Collaborator

deining commented Oct 5, 2022

This moves the configuration of much of the cdn (js/css) into the configuration so they can be more easily maintained.

I like the idea. This PR does not pull in the latest versions of the resources, however (e.g. it pulls in KaTeX 0.15.1, while latest version is 0.16.2.) Were great if this could be improved.

@bradbeam
Copy link
Contributor Author

bradbeam commented Oct 5, 2022

I wanted to keep the scope of the change as minimal as possible. I think version bumps can be done as followups to this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants